Method and system for post authorization payment of transactions using loyalty points

ABSTRACT

A method for confirming post-authorization erasure of a transaction payment using reward points includes: storing account profiles including data related to reward accounts, each including an account identifier and point amount; receiving a transaction message associated with a payment transaction, the message including a specific account identifier and transaction amount; identifying a specific account profile that includes the specific account identifier; calculating a point cost based on the transaction amount; identifying an authorization reference key associated with the payment transaction and specific account profile; identifying a unique identifier associated with the authorization reference key; storing an authorization record including authorization reference key and unique identifier; generating a request message including the identified unique identifier one of: the point cost and transaction amount; and transmitting the request message to a consumer associated with the specific account profile.

FIELD

The present disclosure relates to computerized systems for organizingand indexing of records and files in a manner that facilitate theretrieval of the records and files to facilitate post-authorizationerasure of payment transactions using recorded reward points,specifically the issuing of a rebate message so that a consumer receivesa rebate for a payment transaction after the authorization process hasbeen completed but before a clearing process has been started usingstored reward point values via data value matching using anauthorization key and unique identifier.

BACKGROUND

In an effort to increase revenue, many merchants, manufacturers,retailers, and additional entities may offer consumers a reward orloyalty program. For instance, many merchants may have a specializedloyalty program where a consumer may receive discounts, earn reward orloyalty points, and receive additional perks. In another example, manypayment card issuers offer payment cards to consumers where use thereofcan earn various reward points or other types of benefits from use ofthe payment card, such as cash back, airline miles, etc. These rewardprograms can often encourage a consumer to use a specific paymentmethod, visit a specific merchant, purchase items by a specificmanufacturer, etc.

However, a vast number of these reward programs often require a consumerto redeem their reward points ahead of a transaction. For instance, theconsumer may be required to indicate that they want to make a purchaseusing their reward points prior to even initiating the transaction, ormay be required to indicate reward points when selecting a paymentmethod for a transaction. As a result, many consumers may be unaware oftheir ability to fund certain payment transactions with reward points,and may therefore be missing out on potential savings and opportunities.

As a result, some methods have been developed to provide a consumer withthe opportunity to “erase” a prior transaction using reward points.These methods operate by enabling a consumer to use reward points to geta rebate on a transaction that has previously been settled and cleared.To do so, the consumer uses an interface, such as via a website or anapplication program on a consumer device, to select a specifictransaction and receive a rebate for set number of reward points.However, consumers that are likely to forget to use reward points tofund a transaction may be just as likely to forget to seek out atransaction much later, after clearing, to use their reward points afterthe fact to erase the transaction. In addition, clearing and settlementprocesses can often take a number of days, which may negate the benefitsof erasing a transaction as the consumer's funds would be tied up duringthe duration. Consumers may therefore be more encouraged to use theirreward points for cash back or other rewards, and may fail to takeadvantage of the ability to erase a transaction.

Thus, there is a need for a technical solution to provide improvementsto the computer systems for erasing a payment transaction using rewardpoints. Specifically, there is a need for a better system that providesfor stronger tracking of eligible payment transactions, erasure ofpayment transactions directly after authorization of the transaction,and where erasure is initiated by the system itself and not thecardholder. These technical improvements may result in a system that issignificantly easier for a consumer to use, more effective, and thusresulting in a higher usage rate and thereby more benefits to entitiesinvolved.

SUMMARY

The present disclosure provides a description of systems and methods forpost-authorization erasure of payment transactions using reward points.

A method for confirming post-authorization erasure of a transactionpayment using reward points includes: storing, in an account database, aplurality of account profiles, wherein each account profile includesdata related to a reward account including at least an accountidentifier, a point amount, and contact information; receiving, by areceiving device, a transaction message associated with a paymenttransaction, wherein the transaction message includes at least aspecific account identifier and a transaction amount; identifying, by aprocessing device, a specific account profile stored in the accountdatabase where the included account identifier corresponds to thespecific account identifier included in the received transactionmessage; calculating, by the processing device, a point cost based on atleast the transaction amount included in the received transactionmessage; identifying, by the processing device, an authorizationreference key, wherein the authorization reference key is associatedwith the payment transaction and the identified specific accountprofile; identifying, by the processing device, a unique identifier,wherein the unique identifier is associated with the authorizationreference key; storing, in a record database, an authorization record,wherein the authorization record includes at least the identifiedauthorization reference key and the identified unique identifier;generating, by the processing device, a request message, wherein therequest message includes at least the identified unique identifier andat least one of: the calculated point cost and the transaction amountincluded in the received transaction message; and transmitting, by atransmitting device, the generated request message to a consumerassociated with the identified specific account profile based on theincluded contact information.

A method for post-authorization erasure of a transaction payment usingreward points includes: storing, in an account database, a plurality ofaccount profiles, wherein each account profile includes data related toa reward account including at least an account identifier and a pointamount; storing, in a record database, a plurality of authorizationrecords associated with payment transactions, wherein each authorizationrecord includes at least an authorization key associated with a specificaccount profile and a unique identifier; receiving, by a receivingdevice, an erasure confirmation message, wherein the erasureconfirmation message indicates confirmation for erasure of a paymenttransaction using reward points, the erasure confirmation messageincluding at least a specific unique identifier; identifying, by aprocessing device, a specific authorization record in the recorddatabase where the included unique identifier corresponds to thespecific unique identifier; identifying, by the processing device, aspecific account profile in the account database based on the includedaccount identifier and the authorization key included in the identifiedspecific authorization record; deducting, by the processing device, apoint cost associated with the payment transaction from the point amountincluded in the identified specific account profile; generating, by theprocessing device, a transaction message, wherein the transactionmessage is a request for rebate of a transaction amount of the paymenttransaction; and transmitting, by a transmitting device, the generatedtransaction message to a payment network.

A system for confirming post-authorization erasure of a transactionpayment using reward points a record database, an account database, areceiving device, a processing device, and a transmitting device. Theaccount database is configured to store a plurality of account profiles,wherein each account profile includes data related to a reward accountincluding at least an account identifier, a point amount, and contactinformation. The receiving device is configured to receive a transactionmessage associated with a payment transaction, wherein the transactionmessage includes at least a specific account identifier and atransaction amount. The processing device is configured to: identify aspecific account profile stored in the account database where theincluded account identifier corresponds to the specific accountidentifier included in the received transaction message; calculate apoint cost based on at least the transaction amount included in thereceived transaction message; identify an authorization reference key,wherein the authorization reference key is associated with the paymenttransaction and the identified specific account profile; identify aunique identifier, wherein the unique identifier is associated with theauthorization reference key; store, in the record database, anauthorization record, wherein the authorization record includes at leastthe identified authorization reference key and the identified uniqueidentifier; and generate a request message, wherein the request messageincludes at least the identified unique identifier and at least one of:the calculated point cost and the transaction amount included in thereceived transaction message. The transmitting device is configured totransmit the generated request message to a consumer associated with theidentified specific account profile based on the included contactinformation.

A system for post-authorization erasure of a transaction payment usingreward points includes an account database, a record database, areceiving device, a processing device, and a transmitting device. Theaccount database is configured to store a plurality of account profiles,wherein each account profile includes data related to a reward accountincluding at least an account identifier and a point amount. The recorddatabase is configured to store a plurality of authorization recordsassociated with payment transactions, wherein each authorization recordincludes at least an authorization key associated with a specificaccount profile and a unique identifier. The receiving device isconfigured to receive an erasure confirmation message, wherein theerasure confirmation message indicates confirmation for erasure of apayment transaction using reward points, the erasure confirmationmessage including at least a specific unique identifier. The processingdevice is configured to: identify a specific authorization record in therecord database where the included unique identifier corresponds to thespecific unique identifier; identify a specific account profile in theaccount database based on the included account identifier and theauthorization key included in the identified specific authorizationrecord; deduct a point cost associated with the payment transaction fromthe point amount included in the identified specific account profile;and generate a transaction message, wherein the transaction message is arequest for rebate of a transaction amount of the payment transaction.The transmitting device is configured to transmit the generatedtransaction message to a payment network.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 is a block diagram illustrating a high level system architecturefor post-authorization erasure of payment transactions using rewardpoints in accordance with exemplary embodiments.

FIG. 2 is a block diagram illustrating the processing server of FIG. 1for erasing payment transactions post-authorization using reward pointsin accordance with exemplary embodiments.

FIG. 3 is a flow diagram illustrating a process for erasing paymenttransactions post-authorization using reward points using the system ofFIG. 1 in accordance with exemplary embodiments.

FIG. 4 is a flow diagram illustrating a process for prompting a consumerfor post-authorization erasure of a payment transaction in accordancewith exemplary embodiments.

FIG. 5 is a flow diagram illustrating a process for confirmation anderasure of a payment transaction post-authorization using reward pointsin accordance with exemplary embodiments.

FIGS. 6A and 6B are diagrams illustrating exemplary graphical userinterfaces of a consumer device for post authorization erasure ofpayment transactions using reward points in accordance with exemplaryembodiments.

FIG. 7 is a flow chart illustrating an exemplary method for confirmingpost-authorization erasure of a transaction payment using reward pointsin accordance with exemplary embodiments.

FIG. 8 is a flow chart illustrating an exemplary method forpost-authorization erasure of a transaction payment using reward pointsin accordance with exemplary embodiments.

FIG. 9 is a block diagram illustrating a computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION Glossary of Terms

Payment Network—A system or network used for the transfer of money viathe use of cash-substitutes. Payment networks may use a variety ofdifferent protocols and procedures in order to process the transfer ofmoney for various types of transactions. Transactions that may beperformed via a payment network may include product or servicepurchases, credit purchases, debit transactions, fund transfers, accountwithdrawals, etc. Payment networks may be configured to performtransactions via cash-substitutes, which may include payment cards,letters of credit, checks, transaction accounts, etc. Examples ofnetworks or systems configured to perform as payment networks includethose operated by MasterCard®, VISA®, Discover®, American Express®,PayPal®, etc. Use of the term “payment network” herein may refer to boththe payment network as an entity, and the physical payment network, suchas the equipment, hardware, and software comprising the payment network.

Transaction Account—A financial account that may be used to fund atransaction, such as a checking account, savings account, creditaccount, virtual payment account, etc. A transaction account may beassociated with a consumer, which may be any suitable type of entityassociated with a payment account, which may include a person, family,company, corporation, governmental entity, etc. In some instances, atransaction account may be virtual, such as those accounts operated byPayPal®, etc.

Merchant—An entity that provides products (e.g., goods and/or services)for purchase by another entity, such as a consumer or another merchant.A merchant may be a consumer, a retailer, a wholesaler, a manufacturer,or any other type of entity that may provide products for purchase aswill be apparent to persons having skill in the relevant art. In someinstances, a merchant may have special knowledge in the goods and/orservices provided for purchase. In other instances, a merchant may nothave or require and special knowledge in offered products. In someembodiments, an entity involved in a single transaction may beconsidered a merchant.

Payment Transaction—A transaction between two entities in which money orother financial benefit is exchanged from one entity to the other. Thepayment transaction may be a transfer of funds, for the purchase ofgoods or services, for the repayment of debt, or for any other exchangeof financial benefit as will be apparent to persons having skill in therelevant art. In some instances, payment transaction may refer totransactions funded via a payment card and/or payment account, such ascredit card transactions. Such payment transactions may be processed viaan issuer, payment network, and acquirer. The process for processingsuch a payment transaction may include at least one of authorization,batching, clearing, settlement, and funding. Authorization may includethe furnishing of payment details by the consumer to a merchant, thesubmitting of transaction details (e.g., including the payment details)from the merchant to their acquirer, and the verification of paymentdetails with the issuer of the consumer's payment account used to fundthe transaction. Batching may refer to the storing of an authorizedtransaction in a batch with other authorized transactions fordistribution to an acquirer. Clearing may include the sending of batchedtransactions from the acquirer to a payment network for processing.Settlement may include the debiting of the issuer by the payment networkfor transactions involving beneficiaries of the issuer. In someinstances, the issuer may pay the acquirer via the payment network. Inother instances, the issuer may pay the acquirer directly. Funding mayinclude payment to the merchant from the acquirer for the paymenttransactions that have been cleared and settled. It will be apparent topersons having skill in the relevant art that the order and/orcategorization of the steps discussed above performed as part of paymenttransaction processing.

System for Post-Authorization Erasure of Payment Transactions

FIG. 1 illustrates a system 100 for the post-authorization erasure ofpayment transactions using reward points.

The system 100 may include a processing server 102. The processingserver 102, discussed in more detail below, may be configured toinitiate erasure of payment transactions after authorization usingreward points. In some embodiments, the erasure of payment transactionsmay occur prior to settlement or clearing of the payment transactions.

In the system 100, a consumer 104 may conduct a payment transaction witha merchant 106. The payment transaction may be funded by any suitablepayment method, such as via a payment card, check, etc. Details for thepayment transaction may be transmitted by the merchant 106 (e.g.,directly or via a financial institution, such as an acquiring bank) to apayment network 108 in the form of a transaction message. A transactionmessage may be formatted based on one or more associated standards, suchas the International Organization for Standardization's ISO 8583standard.

The payment network 108 may receive the transaction message, which maybe, for instance, an authorization request (e.g., as indicated in amessage type indicator included therein) and may perform authorizationof the payment transaction using methods and systems that will beapparent to persons having skill in the relevant art. For instance, thepayment network 108 may contact a financial institution associated withthe consumer 104 based on the payment method used to fund thetransaction. For example, if the consumer 104 uses a payment card, thepayment network 108 may contact a financial institution that issued theconsumer 104 the payment card, such as an issuing bank, to approve thetransaction (e.g., based on available credit, fraud rules, etc.).

Once authorization has been completed by the payment network 108, thepayment network 108 may forward the transaction message to theprocessing server 102. In some embodiments, the processing server 102may be a part of the payment network 108. In a further embodiment, theprocessing server 102 may be configured to process payment transactionsas part of the payment network 108. In such an embodiment, thetransaction message may be received by the processing server 102 fromthe merchant 106 and/or a financial institution associated with themerchant, such as for use in processing the corresponding paymenttransaction.

The processing server 102 may, as discussed in more detail below,identify an account profile associated with the consumer 104 based ondata included in the received transaction message. The processing server102 may identify reward points available for use by the consumer 104,and may determine if the payment transaction is eligible for erasure bythe consumer 104. Eligibility may be based on, for instance, thetransaction amount for the payment transaction, available reward pointsfor the consumer 104, rules and limitations associated with the rewardaccount, rules and limitations associated with the transaction or anentity involved therein (e.g., the merchant 106, acquirer, issuer,etc.). If the transaction is eligible for erasure, the processing server102 may generate an authorization reference key associated with thepayment transaction and the account profile of the consumer 104, and mayalso generate a unique identifier associated with the authorizationreference key.

The processing server 102 may then transmit a message to the consumer104 that includes the unique identifier and transaction details for thepayment transaction that indicates to the consumer 104 that thetransaction is eligible for erasure. In some embodiments, the messagemay be transmitted to a consumer device 110 associated with the consumer104 using stored contact information. The consumer device 110 may be,for example, a desktop computer, laptop computer, notebook computer,tablet computer, cellular phone, smart phone, smart watch, wearablecomputing device, implanted computing device, embedded computing device,smart television, etc. The message may be transmitted to the consumer104 via any suitable method, such as short messaging service, multimediamessaging service, e-mail, telephone, an application program, etc.

The consumer 104 may receive the message and may respond to the messageindicating an approval for erasure of the payment transaction usingreward points. The approval may be included in a response that may betransmitted to the processing server 102 via the consumer device 110using the same method as delivery of the first message, or may be sentusing any suitable method. In some embodiments, the consumer 104 may berequired to respond within a predetermined period of time (e.g., 48hours), as indicated in the message provided by the processing server102. In such embodiments, the predetermined period of time may be lessthan an estimated time for clearing and settlement of the transaction.

The processing server 102 may receive the response from the consumer 104and may then deduct the corresponding reward amount from the consumer'saccount profile, and may initiate payment of a rebate to the consumer'stransaction account to erase the payment transaction. The processingserver 102 may track the consumer's response to the appropriatetransaction via the unique identifier and may, via the authorizationreference key, ensure that the appropriate account profile is used forpoint deduction and appropriate transaction account refunded via theerasure. In addition, the use of authorization reference keys and uniqueidentifiers may ensure that the correct transactions are dealt withaccording to consumer instructions in instances where the consumer 104may have received multiple messages for transaction erasures that havetime remaining for a response. For example, if the consumer 104 conductsthree payment transactions in a short period of time, and receives anerasure message for each, the use of the authorization reference key andunique identifier may ensure that each transaction is processedcorrectly based on consumer instructions.

In some embodiments, the processing server 102 may be configured toprovide for partial erasure of payment transactions post authorization.In such an embodiment, a payment transaction may be eligible if theconsumer 104 has a suitable number of reward points eligible for apartial erasure (e.g., as set forth by an issuer, acquirer, the merchant106, etc.). In such embodiments, the consumer 104 may respond to theerasure message with a desired erasure amount, which may be a rewardpoint amount, a transaction amount, a percentage, or other suitablevalue. The processing server 102 may then deduct the corresponding pointamount from the consumer's account profile and may initiate a rebate forthe appropriate transaction amount, with the remaining transactionamount going through the traditional clearing and settlement processes.

The methods and systems discussed herein may enable consumers 104 toerase payment transactions after authorization of the transaction usingreward points in a more efficient and expedited manner than is availableusing traditional systems. By performing the erasure after authorizationof the transaction, the processing server 102 may ensure that theconsumer's funds are not tied up for as long as in traditional systems,and may be able to process rebates and reward transactions faster thanin traditional systems that must wait until clearing and settlement arecompleted. In addition, by using unique identifiers and reference keys,the processing server 102 may more easily track transactions anderasures such that multiple transactions may be considered by a consumer104 at any given time, and may also provide the consumer 104 with theability to erase transactions more easily by requiring less data toproceed in an erasure. For instance, because the processing server 102may not require any information beyond the unique identifier to performan erasure, the consumer's instruction may use less data and maytherefore be transmitted using a number of methods unavailable intraditional systems. In addition, the use of less data may increaseprocessing speed and efficiency, thereby using less system resources.Furthermore, the use of a unique identifier in addition to anauthorization reference key may ensure that no sensitive financial data,such as account numbers, are transmitted to achieve the presentlyclaimed methods and cannot be compromised by a nefarious entity. As aresult, the methods and systems discussed herein provide a significantnumber of technical advantages over traditional systems.

Processing Server

FIG. 2 illustrates an embodiment of the processing server 102 of thesystem 100. It will be apparent to persons having skill in the relevantart that the embodiment of the processing server 102 illustrated in FIG.2 is provided as illustration only and may not be exhaustive to allpossible configurations of the processing server 102 suitable forperforming the functions as discussed herein. For example, the computersystem 900 illustrated in FIG. 9 and discussed in more detail below maybe a suitable configuration of the processing server 102.

The processing server 102 may include a receiving unit 202. Thereceiving unit 202 may be configured to receive data over one or morenetworks via one or more network protocols, including the receipt oftransaction messages via the payment network 108 that are formattedusing associated standards, such as the ISO 8583 standard, andcommunicated using associated specialized communication protocols.Authorization requests may include a plurality of data elements,including data elements configured to store primary account numbers,transaction amounts, merchant data, product data, and additional databased on the associated standards. The receiving unit 202 may alsoreceive messages from consumers 104, such as via consumer devices 110,using appropriate methods, and may also be configured to receive rewarddata associated with consumer reward accounts, such as from merchants106, financial institutions, etc. In some instances, reward accounts maybe managed directly by the processing server 102 and/or payment network108 using methods and systems that will be apparent to persons havingskill in the relevant art.

The processing server 102 may also include an account database 208. Theaccount database 208 may be configured to store a plurality of accountprofiles 210. Each account profile 210 may include data related to areward account associated with one or more consumers 104, including atleast an account identifier, a point amount, and contact information.The account identifier may be a unique value suitable for use inidentification of the account profile 210, related reward account,and/or associated consumer(s) 104, such as an identification number,reward account number, transaction account number, username, emailaddress, device identifier, etc. The point amount may be an amount ofreward points available for use by the associated consumer(s) 104 toerase payment transactions post authorization.

The contact information may include data suitable for use in contactingthe associated consumer 104 and/or a corresponding consumer device 110.The contact information may include, for example, a username, an e-mailaddress, a phone number, a device identifier (e.g., a registrationnumber, a serial number, a media access control address, an internetprotocol address, etc.), or any other type of contact informationsuitable for performing the functions discussed herein as will beapparent to persons having skill in the relevant art.

The processing server 102 may further include a processing unit 204. Theprocessing unit 204 may be configured to perform the functions of theprocessing server 102 discussed herein as will be apparent to personshaving skill in the relevant art. When the receiving unit 202 receivesan authorization request, the processing unit 204 may identify anaccount identifier stored in a data element included in theauthorization request, such as a data element configured to store aprimary account number. The processing unit 204 may then identify anaccount profile 210 stored in the account database 208 that includes theaccount identifier. The processing unit 204 may be configured to thenvalidate eligibility of the payment transaction for erasure.

Eligibility may be based on data associated with the paymenttransaction, such as data stored in one or more data elements includedin the received authorization request, data included in the identifiedaccount profile 210, and additional data, such as associated with amerchant 106 involved in the payment transaction, another financialinstitution involved in the transaction (e.g., an issuer or acquirer),or other consideration. For example, the transaction may be eligible orineligible based on a transaction amount stored in a corresponding dataelement in the authorization request, based on a reward amount in theidentified account profile 210, based on a transaction, product, ormerchant category stored in one or more data elements in theauthorization request, based on a transaction time and/or date stored ina corresponding data element in the authorization request, or acombination thereof.

If the processing unit 204 determines that the transaction is eligiblefor erasure, the processing unit 204 may be configured to generate anauthorization reference key for the transaction. The authorizationreference key may be a unique value associated with the paymenttransaction and the identified account profile 210. In some instances,the authorization reference key may be a transaction identifier, whichmay be stored in a data element included in the received authorizationrequest. The processing unit 204 may store the authorization referencekey in an authorization record 214 in a record database 212 included inthe processing server 102.

The record database 212 may be configured to store a plurality ofauthorization records 214. Each authorization record 214 may includedata related to a payment transaction including at least anauthorization reference key and one or more unique identifiers. In someinstances, each authorization record 214 may be generated and stored inthe record database 212 only for transactions eligible for erasure.Authorization records 214 may also include a status indicator, such asindicative of the status of an erasure. The status may include awaitinga response from the consumer 104, erasure initiated, erasure completed,rebate received, response period expired, etc. Authorization records 214may also include additional data associated with the correspondingpayment transaction, such as a transaction amount and/or theauthorization request.

In some embodiments, an authorization record 214 may include a pointcost. In such an embodiment, the processing unit 204 may be configuredto calculate a reward point cost for erasure of a payment transaction.The reward point cost may be based on the transaction amount for thepayment transaction and one or more conversion rates. Conversion ratesmay be based on the involved merchant 106, an involved financialinstitution, the reward account, products being purchased in the paymenttransaction, or other suitable criteria that will be apparent to personshaving skill in the relevant art.

The processing unit 204 may also be configured to generate uniqueidentifiers. The processing unit 204 may generate a unique identifierfor an authorization record 214 for a payment transaction that iseligible for erasure. In some instances, a single unique identifier maybe generated for each authorization record. In other instances, multipleunique identifiers may be generated, such as one uniquely associatedwith each message to be transmitted to a consumer 104. For example, ifthe processing server 102 transmits multiple erasure notifications to aconsumer 104, each may be associated with a unique identifier. Inanother example, if an account profile 210 is associated with multipleconsumers 104, a different erasure notification may be transmitted toeach consumer 104, with each notification including a different uniqueidentifier.

The processing unit 204 may store unique identifiers in the associatedauthorization records 214. Once an authorization reference key andunique identifier are generated for an eligible transaction, theprocessing unit 204 may generate an erasure notification. The erasurenotification may include at least the unique identifier and one or moretransaction details for the payment transaction, such as the transactionamount or the point cost, and any additional suitable data, such as anexpiration time and/or date. The erasure notification may be transmittedto the consumer 104 using the contact information stored in theidentified account profile 210 by a transmitting unit 206. Thetransmitting unit 206 may be configured to transmit data over one ormore networks via one or more network protocols, including thetransmission of transaction messages via the payment network 108 usingassociated communication protocols.

The consumer 104 may receive the erasure notification via their consumerdevice 110 and may provide a response to the processing server 102. Theresponse may be received by the receiving unit 202 using a suitablemethod. In some embodiments, the response may include only the uniqueidentifier. In other embodiments, the response may include additionalinformation, such as a confirmation from the consumer 104,authentication data, a partial erasure amount, etc. The processing unit204 may identify the data included in the response and may process theerasure accordingly.

Processing of the erasure may include the generating of a transactionmessage for a rebate transaction to rebate a transaction accountassociated with the consumer 104 for the transaction amount or for anamount indicated by the consumer 104 in the response. The generatedtransaction message may be transmitted to the payment network 108 by thetransmitting unit 206 for processing, or may be processing directly bythe processing server 102 in instances where the processing server 102may be a part of the payment network 108 and configured to perform thetraditional functions thereof. The processing unit 204 may also beconfigured to deduct reward points from the point amount stored in theidentified account profile 210. The processing unit 204 may use theassociated authorization record 214, identified via the uniqueidentifier included in the response, to identify the appropriate accountprofile 210 for deduction in instances where multiple responses may bereceived.

In some embodiments, the processing unit 204 may perform additionalvalidation prior to initiation of erasure of a transaction. Forinstance, the processing unit 204 may identify if the ability for theconsumer 104 to erase the transaction has expired (e.g., based on a timeand/or date stored in the authorization record 214), if the consumer 104no longer has the required amount of points available (e.g., due toother erasures or uses of the reward points), etc. In instances wherethe erasure may no longer be valid, the transmitting unit 206 maytransmit a notification to the consumer device 110 indicating such. Insome embodiments, if the erasure is validated and is successfullyperformed, the transmitting unit 206 may transmit a notification to theconsumer device 110.

The processing server 102 may also include a memory 220. The memory 220may be configured to store data for the processing server 110 suitablefor performing the functions disclosed herein. For example, the memory220 may be configured to store standards data for the communication andanalysis of transaction messages, conversion rates for reward points,communication data for communications with consumer devices, rules andalgorithms for validating transactions and reward accounts, etc.Additional data that may be stored in the memory 220 will be apparent topersons having skill in the relevant art.

In some embodiments, the processing server 102 may also include atransaction database 216. The transaction database 216 may be configuredto store a plurality of transaction messages 218. Each transactionmessage 218 may be associated with a payment transaction and may beformatted pursuant to one or more standards associated with theinterchange of transaction messages, such as the ISO 8583 standard. Eachtransaction message 218 may include a plurality of data elementsconfigured to store data including account identifiers, transactionamounts, transaction time and/or dates, and other suitable data. In someembodiments, a transaction message 218 may also be stored with anassociated authorization reference key.

Erasure of Payment Transactions Post-Authorization

FIG. 3 illustrates a process 300 for the erasure of payment transactionspost-authorization using the system 100.

In step 302, the payment network 108 may forward a transaction messagefor a payment transaction to the processing server 102, to be receivedby the receiving unit 202. The transaction message may be formattedbased on one or more standards and include a plurality of data elements,including at least a first data element configured to store a primaryaccount number that includes an account identifier and a second dataelement configured to store a transaction amount. The correspondingpayment transaction may be post-authorization, but may have not yetcleared or settled.

In step 304, the processing unit 204 of the processing server 102 mayidentify and validate a reward account for erasure of the paymenttransaction. The reward account may be identified via identification ofan account profile 210 stored in the account database 208 that includesthe account identifier included in the first data element included inthe received authorization request. The validation may be based on dataincluded in the identified account profile 210 and the receivedauthorization request, such as the reward amount included in theidentified account profile 210 corresponding to the transaction amountstored in the second data element included in the received authorizationrequests. In some embodiments, the validation may include calculation ofa point cost by the processing unit 204, for use in corresponding thereward amount to the transaction amount.

In step 306, an erasure request may be transmitted by the transmittingunit 206 of the processing server 102 to the consumer device 110. Theerasure request may be generated by the processing unit 204 and includeat least a unique identifier and any additional data, such as anexpiration data, a transaction amount, a point cost, etc. Generation ofthe erasure request may also include the generation of an authorizationreference key and the unique identifier, which may be stored in anauthorization record 214 in the record database 212. The transmittingunit 206 may transmit the request to the consumer device 110 usingcontact information stored in the identified account profile 210.

In step 308, the consumer device 110 may prompt the consumer 104 forerasure. The prompt may include the display of the erasure request tothe consumer 104 and the prompting or a response to be entered by theconsumer 104 to initiate erasure. In step 310, the consumer device 110may transmit an erasure confirmation to the processing server 102, to bereceived by the receiving unit 202. The erasure confirmation may includeat least the unique identifier that had been included in the erasurerequest transmitted in step 306.

In step 312, the processing unit 204 may identify the account profile210 again based on information stored in the authorization record 214(e.g., the authorization reference key) that includes the uniqueidentifier included in the erasure confirmation, and may deduct thepoint cost from the reward amount stored in the account profile 210. Inembodiments where partial erasure may be available to the consumer 104,the deducted reward amount may be based on an amount included in thereceived erasure confirmation.

In step 314, the processing server 102 may initiate a rebate with thepayment network 108 for rebate of the transaction amount (e.g., or aportion thereof) to the consumer 104. Initiation of the rebate mayinclude the generation of a transaction message, such as anauthorization request, for the rebate by the processing unit 204 thatincludes the transaction amount, an account identifier associated withthe consumer 104 (e.g., or a transaction account associated thereto),and any other suitable data, and the transmission thereof to the paymentnetwork 108 by the transmitting unit 206 of the processing server 102.

In step 316, the payment network 108 may process the rebate usingmethods and systems that will be apparent to persons having skill in therelevant art. In step 318, a rebate confirmation may be transmitted tothe consumer device 110 by the payment network 108 using methods andsystems that will be apparent to persons having skill in the relevantart.

Process for Requesting Post-Authorization Erasure of TransactionPayments

FIG. 4 illustrates a process 400 for the validation of a paymenttransaction and requesting of erasure thereof by the consumer 104 usingthe processing server 102.

In step 402, account profiles 210 may be stored in the account database208 of the processing server 112, wherein each account profile 210includes data related to a reward account including at least an accountidentifier, a point amount, and contact information. In step 404, thereceiving unit 202 of the processing server 102 may receive atransaction message for a payment transaction. The transaction messagemay be formatted based on one or more standards and may include aplurality of data elements, including data elements configured to storea specific account identifier and a transaction amount.

In step 406, the processing unit 204 of the processing server 102 maydetermine if the transaction is eligible for erasure. The determinationmay be based on data stored in the plurality of data elements includedin the received authorization request and additional data, such asrequirements set forth by the merchant 106, a financial institution, theprocessing server 102, the payment network 108, etc. For instance, themerchant 106 involved in the payment transaction may prohibit erasurefor transactions under ten dollars. In another example, an issuing bankmay prohibit erasure for transactions involving gambling. If thetransaction is determined to be ineligible for erasure, the process 400may be completed.

If the transaction is determined to be eligible, then, in step 408, theprocessing unit 204 may identify the account profile 210 for the rewardaccount involved in the transaction. The account profile 210 may beidentified based on inclusion of the specific account identifier storedin a data element included in the received authorization request. Instep 410, the processing unit 204 may calculate the point cost forerasure of the payment transaction. The point cost may be based on thetransaction amount stored in a data element included in the receivedauthorization request and, in some instances, a conversion rate. In someembodiments, the point cost may have been previously calculated by theprocessing unit 204 in step 406 while determining transactioneligibility.

In step 412, the processing unit 204 may determine if the reward accountis eligible for erasure of the transaction. The determination may bebased on a correspondence between the calculated point cost and thereward amount available in the identified account profile 210, and anyadditional information stored in the identified account profile 210. Ifthe reward account is not eligible for erasure of the transaction, thenthe process 400 may be completed. If the reward account is eligible,then, in step 414, the processing unit 204 may generate an authorizationrecord 214. Generation of the authorization record may includegeneration of an authorization reference key associated with the paymenttransaction and the identified account profile 210 and generation of aunique identifier associated with the authorization reference key. Theauthorization record 214 may be stored in the record database 212. Insome embodiments, the authorization record 214 may also include anexpiration time and/or date, a status indicator, the point cost, and/orthe received transaction message or data included therein.

In step 416, the processing unit 204 may generate an erasure requestmessage. The erasure request message may include at least the uniqueidentifier and the calculated point cost and/or the transaction amountstored in the data element in the authorization request. In someembodiments, the erasure request message may include additional data,such as response instructions, the expiration time and/or date, etc. Instep 418, the transmitting unit 206 of the processing server 102 maytransmit the erasure request message to the consumer device 110associated with the reward account using the contact informationincluded in the identified account profile 210.

Processing of Post-Authorization Erasure of Transaction Payments

FIG. 5 illustrates a process 500 for the post-authorization erasure oftransaction payments following confirmation from the consumer 104 usingthe processing server 102.

In step 502, the processing server 102 may store account profiles 210 inthe account database 208 and authorization records 214 in the recorddatabase 208. Each account profile 210 may include data related to areward account including at least an account identifier, a point amount,and contact information. Each authorization record 214 may include datarelated to a payment transaction including at least an authorizationreference key associated with the transaction and a specific accountprofile and a unique identifier. In some embodiments, each authorizationrecord 214 may also include a point cost, a transaction message, astatus indicator, and/or an expiration time and/or date.

In step 504, the receiving unit 202 of the processing server 102 mayreceive an erasure confirmation message from a consumer device 110. Theerasure confirmation message may include at least a specific uniqueidentifier. In some embodiments, the erasure confirmation message mayalso include an erasure amount, which may correspond to a currencyamount or a reward point amount. In step 506, the processing unit 204 ofthe processing server 102 may identify an authorization record 214corresponding to the erasure confirmation message based on inclusion ofthe specific unique identifier.

In step 508, the processing unit 204 may determine if the correspondingpayment transaction is still eligible for erasure. The determination maybe made based on a status indicator included in the identifiedauthorization record 214 or an expiration time and/or date included inthe identified authorization record 214. For example, if the statusindicator indicates that the transaction was already erased, or if theavailable time period for erasure has expired, the transaction may nolonger be eligible, such as to prevent multiple rebates on a singletransaction or to prohibit interference with clearing and settlementprocesses.

If the transaction is determined to be ineligible for erasure, then, instep 510, the transmitting unit 206 of the processing server 102 maytransmit a notification to the consumer device 110 that indicates thatthe transaction is no longer valid. In some embodiments, thenotification may include a message that indicates a reason for theinvalidation (e.g., that the time period expired). If the transaction isdetermined to be eligible, then, in step 512, the processing unit 204may identify an account profile 210 associated with the paymenttransaction to be erased. The account profile 210 may be identifiedbased on the authorization reference key included in the identifiedauthorization record and the account identifier stored in the accountprofile 210.

In step 514, the processing unit 204 may determine if the account isstill eligible for erasure of the payment transaction. The determinationmay be based on the current in reward amount and any additional dataand/or settings included in the identified account profile 210. Forinstance, if the consumer 104 spent reward points in between the sendingof the erasure request and receipt of the erasure confirmation message,the reward account may lose eligibility for erasure of the transaction(e.g., due to insufficient reward points). If the account is no longereligible, then, in step 516, the transmitting unit 206 may transmit anotification to the consumer device 110 that indicates that the accountis no longer eligible. In some embodiments, the notification may includea message indicating the reasoning.

If, in step 514, the processing unit 204 determines that the rewardaccount is eligible, then, in step 518, the processing unit 204 maydeduct the point cost from the reward amount included in the identifiedaccount profile 210. In some embodiments, the point cost may be includedin the identified authorization record 214. In other embodiments, thepoint cost may be calculated by the processing unit 204 using themethods discussed herein. In step 520, the processing unit 204 maygenerate a transaction message for a rebate for the payment transactionfor the transaction amount (e.g., or for a lesser amount as indicated inthe erasure confirmation message), which may be transmitted by thetransmitting unit 206 to the payment network 108 for processing. In someembodiments, initiation of the rebate may include the updating of astatus indicator included in the identified authorization record 214,such as to indicate that the rebate is being processed. In step 522, thetransmitting unit 206 may transmit a notification to the consumer device110 confirming that the transaction is being erased.

Graphical User Interface

FIGS. 6A and 6B illustrate a graphical user interface of the consumerdevice 110 for use in the erasure of payment transactions postauthorization using reward points. It will be apparent to persons havingskill in the relevant art that the interfaces illustrated in FIGS. 6Aand 6B and discussed herein are provided as illustration only, and thatadditional and/or alternative interfaces may be used in accomplishingthe methods and systems discussed herein.

The consumer device 110 may include a display 602. The display 602 maybe configured to display data to a user of the consumer device 110, suchas the consumer 104, using methods and systems that will be apparent topersons having skill in the relevant art. As illustrated in FIG. 6A, thedisplay 602 may be configured to display an application program for thereceipt and transmission of messages, such as short messaging servicemessages. The display 602 may display an erasure request message 604.

The erasure request message 604 may include at least the uniqueidentifier associated with the corresponding payment transaction,illustrated in FIG. 6A as an identification number with a value of18560. The erasure request message 604 may also include transactiondata, such as the transaction amount ($26.42), the merchant name (MainStreet Café), and the transaction date (Jan. 1, 2015). The erasurerequest message 604 may also include a calculated point cost (1,918points) as well as account data, such as available reward points (29,203points). The erasure request message 604 may also include responseinstructions. As illustrated in FIG. 6A, if the consumer 104 wants toconfirm erasure of the transaction, they are asked to respond to theerasure request message with a message of “YES.”

The display 602 may also display an input 606 and a send button 608. Theinput 606 may be used to receive input from the user of the consumerdevice 110, such as text that may be entered via one or more inputdevices. The send button 608 may, when interacted with by the user, sendthe content of the input 606 in a response message as a response to thereceived erasure request message 604. If the consumer 104 wants to erasethe indicated payment transaction, the consumer 104 may enter “YES” intothe input 606 and interact with the send button 608. In someembodiments, the consumer 104 may also send the unique identifier in theresponse message.

FIG. 6B illustrates the receipt of an erasure confirmation message 610,such as received following the response of the consumer 104 to theerasure request message 604 with a “YES” message. The erasureconfirmation message 610 may include confirmation data, such astransaction data that confirms which transaction was erased (e.g., thetransaction amount, transaction date, and merchant name as illustratedin FIG. 6B), as well as account data, such as the reward pointsremaining for the reward account following erasure.

Exemplary Method for Confirming Post-Authorization Erasure of aTransaction Payment Using Reward Points

FIG. 7 illustrates a method 700 for prompting a consumer forconfirmation of erasure of a transaction payment post authorization ofthe transaction using reward points.

In step 702, a plurality of account profiles (e.g., account profiles210) may be stored in an account database (e.g., the account database208), wherein each account profile 210 includes data related to a rewardaccount including at least an account identifier, a point amount, andcontact information. In step 704, a transaction message associated witha payment transaction may be received by a receiving device (e.g., thereceiving unit 202), wherein the transaction message includes at least aspecific account identifier and a transaction amount. In one embodiment,the associated payment transaction has been authorization but has notbeen cleared.

In step 706, a specific account profile 210 stored in the accountdatabase 208 may be identified by a processing device (e.g., theprocessing unit 204) where the included account identifier correspondsto the specific account identifier included in the received transactionmessage. In step 708, a point cost may be calculated by the processingdevice 204 based on at least the transaction amount included in thereceived transaction message. In step 710, an authorization referencekey may be identified by the processing device 204, wherein theauthorization reference key is associated with the payment transactionand the identified specific account profile 210.

In step 712, a unique identifier may be identified by the processingdevice 204, wherein the unique identifier is associated with theauthorization reference key. In step 714, an authorization record (e.g.,authorization record 214) may be stored in a record database (e.g., therecord database 212), wherein the authorization record 214 includes atleast the identified authorization reference key and the identifiedunique identifier. In step 716, a request message may be generated bythe processing device 204, wherein the request message includes at leastthe identified unique identifier and at least one of: the calculatedpoint cost and the transaction amount included in the receivedtransaction message.

In step 718, the generated request message may be transmitted by atransmitting device (e.g., the transmitting unit 206) to a consumer(e.g., the consumer 104) associated with the identified specific accountprofile 210 based on the included contact information. In someembodiments, the generated request message may not be transmitted to theconsumer 104 if the point amount included in the identified specificaccount profile 210 is less than the calculated point cost. In oneembodiment, the method 700 may further include validating, by theprocessing device 204, the associated payment transaction as an eligiblepayment transaction based on transaction data further included in thereceived transaction message.

In some embodiments, the method 700 may also include validating, by theprocessing device 204, the identified specific account profile 210 aseligible for erasure of the transaction amount included in the receivedtransaction message based on at least one of: account data furtherincluded in the identified specific account profile 210 and a comparisonof the calculated point cost and the point amount included in theidentified specific account profile 210. In one embodiment, the method700 may further include: receiving, by the receiving device 202, anerasure confirmation from the consumer 104 in response to thetransmitted request message; deducting, by the processing device 204,the point cost from the point amount included in the identified specificaccount profile 210; and transmitting, by the transmitting device 206,an authorization transaction message requesting a rebate of thetransaction amount for the associated payment transaction to a paymentnetwork (e.g., the payment network 108).

Exemplary Method for Post-Authorization Erasure of a Transaction PaymentUsing Reward Points

FIG. 8 illustrates a method 800 for the erasure of a transaction paymentpost authorization using reward points based on a consumer instruction.

In step 802, a plurality of account profiles (e.g., account profiles210) may be stored in an account database (e.g., the account database208), wherein each account profile 210 includes data related to a rewardaccount including at least an account identifier and a point amount. Instep 804, a plurality of authorization records (e.g., authorizationrecords 214) associated with payment transactions may be stored in arecord database (e.g., the record database 212), wherein eachauthorization record 214 includes at least an authorization keyassociated with a specific account profile 210 and a unique identifier.

In step 806, an erasure confirmation message may be received by areceiving device (e.g., the receiving unit 202), wherein the erasureconfirmation message indicates confirmation for erasure of a paymenttransaction using reward points, the erasure confirmation messageincluding at least a specific unique identifier. In step 808, a specificauthorization record 214 in the record database 212 may be identified bya processing device (e.g., the processing unit 204) where the includedunique identifier corresponds to the specific unique identifier.

In step 810, a specific account profile 210 in the account database 208may be identified by the processing device 204 based on the includedaccount identifier and the authorization key included in the identifiedspecific authorization record 214. In step 812, a point cost associatedwith the payment transaction may be deducted, by the processing device204, from the point amount included in the identified specific accountprofile 210. In one embodiment, the identified specific authorizationrecord 214 may include the point cost.

In step 814, a transaction message may be generated by the processingdevice 204, wherein the transaction message is a request for rebate of atransaction amount of the payment transaction. In step 816, thegenerated transaction message may be transmitted by a transmittingdevice (e.g., the transmitting unit 206) to a payment network (e.g., thepayment network 108). In some embodiments, the identified specificauthorization record 214 may further include a received transactionmessage, the received transaction message including at least atransaction amount, and the method 800 may further include calculating,by the processing device 204, a point cost based on at least thetransaction amount included in the received transaction message includedin the identified specific authorization record.

In one embodiment, each authorization record 214 may further include astatus identifier. In a further embodiment, the method 800 may furtherinclude validating, by the processing device 204, the paymenttransaction as an eligible payment transaction based on the statusidentifier included in the identified specific authorization record 214.In another further embodiment, the method 800 may also include updating,in the identified specific authorization record 214, the statusidentifier to indicate that the associated payment transaction has beenerased.

In some embodiments, the method 800 may further include validating, bythe processing device 204, the identified specific account profile 210as eligible for erasure of the payment transaction based on the pointamount included in the identified specific account profile 210 and thepoint cost. In one embodiment, the method 800 may also includetransmitting, by the transmitting device 206, a confirmation message toa consumer (e.g., the consumer 104), associated with the identifiedspecific account profile 210, wherein the confirmation message indicateserasure of the payment transaction.

Computer System Architecture

FIG. 9 illustrates a computer system 900 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the processing server 102 of FIG. 1may be implemented in the computer system 900 using hardware, software,firmware, non-transitory computer readable media having instructionsstored thereon, or a combination thereof and may be implemented in oneor more computer systems or other processing systems. Hardware,software, or any combination thereof may embody modules and componentsused to implement the methods of FIGS. 3-5, 7, and 8.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. A personhaving ordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computers linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device. For instance, at least oneprocessor device and a memory may be used to implement the abovedescribed embodiments.

A processor unit or device as discussed herein may be a singleprocessor, a plurality of processors, or combinations thereof. Processordevices may have one or more processor “cores.” The terms “computerprogram medium,” “non-transitory computer readable medium,” and“computer usable medium” as discussed herein are used to generally referto tangible media such as a removable storage unit 918, a removablestorage unit 922, and a hard disk installed in hard disk drive 912.

Various embodiments of the present disclosure are described in terms ofthis example computer system 900. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormulti-processor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 904 may be a special purpose or a general purposeprocessor device. The processor device 904 may be connected to acommunications infrastructure 906, such as a bus, message queue,network, multi-core message-passing scheme, etc. The network may be anynetwork suitable for performing the functions as disclosed herein andmay include a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 900 may also include a main memory 908(e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 910. The secondary memory 910 may include thehard disk drive 912 and a removable storage drive 914, such as a floppydisk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 914 may read from and/or write to theremovable storage unit 918 in a well-known manner. The removable storageunit 918 may include a removable storage media that may be read by andwritten to by the removable storage drive 914. For example, if theremovable storage drive 914 is a floppy disk drive or universal serialbus port, the removable storage unit 918 may be a floppy disk orportable flash drive, respectively. In one embodiment, the removablestorage unit 918 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 910 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 900, for example, the removable storage unit922 and an interface 920. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 922 and interfaces920 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 900 (e.g., in the main memory 908and/or the secondary memory 910) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 900 may also include a communications interface 924.The communications interface 924 may be configured to allow software anddata to be transferred between the computer system 900 and externaldevices. Exemplary communications interfaces 924 may include a modem, anetwork interface (e.g., an Ethernet card), a communications port, aPCMCIA slot and card, etc. Software and data transferred via thecommunications interface 924 may be in the form of signals, which may beelectronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 926, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

The computer system 900 may further include a display interface 902. Thedisplay interface 902 may be configured to allow data to be transferredbetween the computer system 900 and external display 930. Exemplarydisplay interfaces 902 may include high-definition multimedia interface(HDMI), digital visual interface (DVI), video graphics array (VGA), etc.The display 930 may be any suitable type of display for displaying datatransmitted via the display interface 902 of the computer system 900,including a cathode ray tube (CRT) display, liquid crystal display(LCD), light-emitting diode (LED) display, capacitive touch display,thin-film transistor (TFT) display, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 908 and secondary memory 910, whichmay be memory semiconductors (e.g., DRAMs, etc.). These computer programproducts may be means for providing software to the computer system 900.Computer programs (e.g., computer control logic) may be stored in themain memory 908 and/or the secondary memory 910. Computer programs mayalso be received via the communications interface 924. Such computerprograms, when executed, may enable computer system 900 to implement thepresent methods as discussed herein. In particular, the computerprograms, when executed, may enable processor device 904 to implementthe methods illustrated by FIGS. 3-5, 7, and 8, as discussed herein.Accordingly, such computer programs may represent controllers of thecomputer system 900. Where the present disclosure is implemented usingsoftware, the software may be stored in a computer program product andloaded into the computer system 900 using the removable storage drive914, interface 920, and hard disk drive 912, or communications interface924.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for post-authorization erasure oftransaction payments using reward points. While various exemplaryembodiments of the disclosed system and method have been described aboveit should be understood that they have been presented for purposes ofexample only, not limitations. It is not exhaustive and does not limitthe disclosure to the precise form disclosed. Modifications andvariations are possible in light of the above teachings or may beacquired from practicing of the disclosure, without departing from thebreadth or scope.

What is claimed is:
 1. A method for post-authorization erasure of atransaction payment using reward points, comprising: storing, in anaccount database, a plurality of account profiles, wherein each accountprofile includes data related to a reward account including at least anaccount identifier and a point amount; storing, in a record database, aplurality of authorization records associated with payment transactions,wherein each authorization record includes at least an authorization keyassociated with a specific account profile and a unique identifier;receiving, by a receiving device, an erasure confirmation message,wherein the erasure confirmation message indicates confirmation forerasure of a payment transaction using reward points, the erasureconfirmation message including at least a specific unique identifier;identifying, by a processing device, a specific authorization record inthe record database where the included unique identifier corresponds tothe specific unique identifier; identifying, by the processing device, aspecific account profile in the account database based on the includedaccount identifier and the authorization key included in the identifiedspecific authorization record; deducting, by the processing device, apoint cost associated with the payment transaction from the point amountincluded in the identified specific account profile; generating, by theprocessing device, a transaction message, wherein the transactionmessage is a request for rebate of a transaction amount of the paymenttransaction; and transmitting, by a transmitting device, the generatedtransaction message to a payment network.
 2. The method of claim 1,wherein the identified specific authorization record further includesthe point cost.
 3. The method of claim 1, wherein the identifiedspecific authorization record further includes a received transactionmessage, the received transaction message including at least atransaction amount, and wherein the method further comprises:calculating, by the processing device, a point cost based on at leastthe transaction amount included in the received transaction messageincluded in the identified specific authorization record.
 4. The methodof claim 1, wherein each authorization record further includes a statusidentifier.
 5. The method of claim 4, further comprising: validating, bythe processing device, the payment transaction as an eligible paymenttransaction based on the status identifier included in the identifiedspecific authorization record.
 6. The method of claim 4, furthercomprising: updating, in the identified specific authorization record,the status identifier to indicate that the associated paymenttransaction has been erased.
 7. The method of claim 1, furthercomprising: validating, by the processing device, the identifiedspecific account profile as eligible for erasure of the paymenttransaction based on the point amount included in the identifiedspecific account profile and the point cost.
 8. The method of claim 1,further comprising: transmitting, by the transmitting device, aconfirmation message to a consumer associated with the identifiedspecific account profile, wherein the confirmation message indicateserasure of the payment transaction.
 9. A system for post-authorizationerasure of a transaction payment using reward points, comprising: anaccount database configured to store a plurality of account profiles,wherein each account profile includes data related to a reward accountincluding at least an account identifier and a point amount; a recorddatabase configured to store a plurality of authorization recordsassociated with payment transactions, wherein each authorization recordincludes at least an authorization key associated with a specificaccount profile and a unique identifier; a receiving device configuredto receive an erasure confirmation message, wherein the erasureconfirmation message indicates confirmation for erasure of a paymenttransaction using reward points, the erasure confirmation messageincluding at least a specific unique identifier; a processing deviceconfigured to: identify a specific authorization record in the recorddatabase where the included unique identifier corresponds to thespecific unique identifier, identify a specific account profile in theaccount database based on the included account identifier and theauthorization key included in the identified specific authorizationrecord, deduct a point cost associated with the payment transaction fromthe point amount included in the identified specific account profile,and generate a transaction message, wherein the transaction message is arequest for rebate of a transaction amount of the payment transaction;and a transmitting device configured to transmit the generatedtransaction message to a payment network.
 10. The system of claim 9,wherein the identified specific authorization record further includesthe point cost.
 11. The system of claim 9, wherein the identifiedspecific authorization record further includes a received transactionmessage, the received transaction message including at least atransaction amount, and the processing device is further configured tocalculate a point cost based on at least the transaction amount includedin the received transaction message included in the identified specificauthorization record.
 12. The system of claim 9, wherein eachauthorization record further includes a status identifier.
 13. Thesystem of claim 12, wherein the processing device is further configuredto validate the payment transaction as an eligible payment transactionbased on the status identifier included in the identified specificauthorization record.
 14. The system of claim 12, wherein the processingdevice is further configured to update, in the identified specificauthorization record, the status identifier to indicate that theassociated payment transaction has been erased.
 15. The system of claim9, wherein the processing device is further configured to validate theidentified specific account profile as eligible for erasure of thepayment transaction based on the point amount included in the identifiedspecific account profile and the point cost.
 16. The system of claim 9,wherein the transmitting device is further configured to transmit aconfirmation message to a consumer associated with the identifiedspecific account profile, wherein the confirmation message indicateserasure of the payment transaction.